ftp.cs.arizona.edu/ftp.cs.arizona.edu.tar/ftp.cs.arizona.edu/icon/newsgrp/group98c.txt/000070_icon-group-sender _Tue Nov 3 12:32:54 1998.msg

Internet Message Format | 2000-09-20 | 2KB

Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
    by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) with SMTP id MAA19784
    for <[e-mail]>; Tue, 3 Nov 1998 12:32:53 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
    id AA13943; Tue, 3 Nov 1998 12:32:15 -0700
Date: Tue, 3 Nov 1998 09:17:45 -0700
From: Gregg Townsend <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail], [e-mail]
Subject: Re:  System Stack Overflow
Errors-To: [e-mail]
Status: RO

    From: Richard Laing <[e-mail]>

    "Unfortunately, system stack overflow may not be detected..."

    So - how serious is this?  Does it mean the system will crash,
    and therefore you will KNOW there is a problem?  Or is it possible
    the program will continue to run but with bad data/results?


On Unix systems, the application can't cause a system crash, and
it is very rare for stack overflow to be a problem.  I've only seen
it when co-expressions were used.  In those few cases, it was clear
that something was wrong, although the cause was not at all obvious.

I can't really answer regarding Windows systems, but I would venture
to guess that you most likely WILL know there is something wrong.

   ---------------------------------------------------------------------------
   Gregg Townsend              Gould-Simpson Building   [e-mail]
   Staff Scientist             1040 E. 4th St.          32 13 45N  110 57 16W
   Dept. of Computer Science   PO Box 210077            tel: [phone]
   The University of Arizona   Tucson, AZ  85721-0077   fax: [phone]